Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: pull latest image from registry when using build server #4771

Merged
merged 2 commits into from
Feb 12, 2025

Conversation

lucienbl
Copy link
Contributor

@lucienbl lucienbl commented Jan 8, 2025

Changes

  • This fixes an issue where new preview images are not pulled from the registry when using a build server causing the preview deployment to not being updated as expected

Issues

@andrasbacsai
Copy link
Member

@coderabbitai review

Copy link

coderabbitai bot commented Feb 12, 2025

📝 Walkthrough

Summary by CodeRabbit

  • New Features
    • Deployment processes now automatically pull the latest container images, ensuring that your applications run with the most up-to-date versions for improved performance and reliability.

Walkthrough

The pull request updates the Docker Compose command within the start_by_compose_file method of the application deployment job. The command has been modified to include the --pull always option, ensuring that the latest container images are fetched from the registry during deployment. There are no changes to public or exported declarations.

Changes

File Change Summary
app/Jobs/ApplicationDeploymentJob.php Modified the Docker Compose command in the start_by_compose_file method to add the --pull always option.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
app/Jobs/ApplicationDeploymentJob.php (1)

2267-2279: Consider adding --pull always in other Docker Compose commands for consistency.

While the change fixes the issue for build server deployments, consider adding the --pull always flag in other Docker Compose commands for consistency:

  1. Line 2277: When not using a build server, the images might not be pulled if they exist locally.

Note: The dockerimage buildpack case (line 2268) already has a separate pull command, so it's not affected.

Apply this diff to ensure consistent behavior:

-                    [executeInDocker($this->deployment_uuid, "{$this->coolify_variables} docker compose --project-name {$this->application->uuid} --project-directory {$this->workdir} -f {$this->workdir}{$this->docker_compose_location} up --build -d"), 'hidden' => true],
+                    [executeInDocker($this->deployment_uuid, "{$this->coolify_variables} docker compose --project-name {$this->application->uuid} --project-directory {$this->workdir} -f {$this->workdir}{$this->docker_compose_location} up --pull always --build -d"), 'hidden' => true],
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1fe4dd7 and a139cf1.

📒 Files selected for processing (1)
  • app/Jobs/ApplicationDeploymentJob.php (1 hunks)
🔇 Additional comments (1)
app/Jobs/ApplicationDeploymentJob.php (1)

2273-2274: LGTM! The change ensures latest images are pulled.

The addition of --pull always to the Docker Compose command ensures that the latest container images are always pulled from the registry before starting containers, which fixes the issue with preview images not being pulled when using a build server.

@andrasbacsai
Copy link
Member

Thank you for the PR!

@andrasbacsai andrasbacsai merged commit 619a42b into coollabsio:next Feb 12, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants